Proximity detection of mobile devices for emergency calling

ABSTRACT

A system and method for placing an emergency call using a initiating device. A initiating device receives a request to place an emergency call. Upon determining that a VoIP-based emergency call cannot be placed, the initiating device identifies a proximate proxy device. The initiating device directs the proxy device to place the emergency call.

BACKGROUND OF THE INVENTION

Reliability in making emergency calls is an important feature of anyphone service. In the United States, emergency calls are handled throughthe 9-1-1 system, which originated in the era of landline telephones.The 9-1-1 system originally relied on the assumption that each phone ispermanently present at a specific geographical location (e.g., aresidential or business street address). The subsequent development ofmobile calling devices has created technical hurdles to emergencycalling. Because a mobile calling device can potentially make emergencycalls from any location within a vast geographical area (e.g., at leastthe entire United States), additional steps beyond the connection of anemergency call itself are necessary to ensure that emergency servicescan be accurately dispatched to a caller's location.

Emergency services can be dispatched in response to an emergency call. Acaller can initiate an emergency call (e.g., from a landline telephone,mobile phone, or other calling device) by dialing an emergency number(e.g., 9-1-1 in the United States). The emergency number connects thecaller to an appropriate public-safety answering point (“PSAP”) (e.g., a9-1-1 dispatch center). The PSAP is selected on the basis of thecaller's geographical location, as explained in more detail below. Thecaller is connected to an operator at the PSAP. Upon determining thenature of the emergency call, the operator dispatches appropriateemergency services to the caller's location if an emergency thatrequires a response by emergency services actually exists.

The selection of an appropriate PSAP is crucial because each PSAP isresponsible for dispatching emergency services within a specificgeographical area (e.g., a city or county), and a given PSAP can onlydirectly dispatch emergency services to locations within its specificgeographical area. When routing an emergency call to a PSAP, it istherefore essential that the selected PSAP is one whose geographicalarea of responsibility includes the caller's current location.Therefore, selecting an appropriate PSAP requires ascertaining thecaller's geographical location. If a caller dialing 9-1-1 is connectedto an inappropriate PSAP, the dispatcher at that PSAP will be powerlessto help the caller even if the caller's geographical location is known.Even though a dispatcher at an inappropriate PSAP may know where thecaller is dialing from by means of dialogue with the caller, thedispatcher is nonetheless unable to directly send emergency services tothat location because the location is outside the PSAP's geographicalarea of responsibility. In an emergency situation, response times arecrucial, and any delay can mean the difference between life and death.

For PSTN telephones, ensuring the selection of an appropriate PSAP isstraightforward. Because a traditional PSTN telephone is necessarilyassociated with a specific geographical location, a phone company cancreate a record associating that traditional PSTN telephone with anappropriate PSAP. Emergency calls from that traditional PSTN telephonewill be routed, according to that record, to the corresponding PSAP.

For mobile phones, the Enhanced 911 (“E911”) system provides astandardized technological solution for routing emergency calls. When anemergency call is placed using a mobile phone with E911-compliantservice, the phone's current location information is made available tothe E911 system, which then selects an appropriate PSAP on the basis ofthat information. In practice, the location information is derived fromGlobal Positioning System (“GPS”) data supplied by the phone itself,cell-tower triangulation, or a combination thereof. Though E911 is notinfallible, it is a generally reliable solution for handling emergencycalls from mobile phones.

The increasing adoption of Voice over Internet Protocol (“VoIP”)technology has introduced technological challenges beyond thosecurrently addressed by E911. First, VoIP service is a so-called“over-the-top” (“OTT”) service. The term “OTT” refers to any servicewhose data is transmitted as general network traffic over a preexistingInternet connection. The OTT nature of VoIP service limits the abilityof an initiating device to ascertain its own geographical location. Ingeneral, an initiating device, when making a call, is “aware” only ofthe fact that an underlying network connection is available.Accordingly, the initiating device is “ignorant” of additionalinformation concerning the network connection that could otherwise beuseful in determining its geographical location. Such additionalinformation may, for example, include the identity and geographicallocation of the cell tower supplying the network connection.

Second, while methods have been developed for tracking the location ofcertain initiating devices through measures that operate independentlyof VoIP service (e.g., separately maintained location records), thosemethods are subject to technological constraints that limit thecircumstances in which reliable location information can be obtained.Consequently, mobile devices (e.g., laptop computers) often offer noemergency calling at all.

Emergency calling through VoIP is further complicated when initiatingdevices can be associated with phone numbers from the public switchedtelephone network (“PSTN”), as is the case in business-oriented VoIPservices (e.g., Skype for Business™). For businesses, the availabilityof PSTN phone numbers is often desirable because an initiating devicecan keep the same PSTN phone number regardless of its actual geographiclocation. This, however, may lead to misrouted emergency calls. Becausethe E911 system cannot reliably distinguish between an initiating devicewith a PSTN phone number and a “true” PSTN device (e.g., a traditionalPSTN telephone or mobile phone), the E911 system may be unable tocorrectly identify the geographical location of an initiating device.

For consumer-grade VoIP services (e.g., consumer Skype® service), thedifficulties are even greater. Because such services generally do notassociate user accounts with PSTN phone numbers, PSTNcaller-identification systems cannot provide meaningful identificationconcerning the origin of a call from a consumer-oriented VoIP service.In practice, the “origin number” of a call made from a consumer-orientedVoIP account may be an “unknown caller” indication, an arbitrary PSTNphone number with no relationship to the caller, or a series of digitsthat do not constitute a valid PSTN phone number (e.g., “000-000-0000”).If an emergency call is made from a consumer-oriented VoIP account, theE911 system will be unable to route the call to the appropriate PSAP.

Without a way to accurately determine the geographical origin of aVoIP-based emergency call, the call may be disconnected, routed to anincorrect PSAP, or routed to an inappropriate phone line within a PSAP(e.g., an administrative phone line, as opposed to a phone lineconnecting to 911 dispatchers).

VoIP services have generally addressed the problem of emergency callingby associating each initiating device with a registered location. As apractical matter, the registered location of an initiating device isusually defined in advance of using the device (e.g., immediately uponthe activation of VoIP service). While a registered location can, inprinciple, be any location to which emergency services can bedispatched, a registered location is typically a home address (if theinitiating device is for personal use) or an office address (if theinitiating device is for business use). Emergency calling from theinitiating device is enabled only when the device is confirmed to bepresent at its registered location. The registered location of a VoIPdesk phone, for instance, may be the street address of the officebuilding in which the phone is located. When an emergency call is placedfrom the phone, the location of the phone may be confirmed in variousways (e.g., by verifying that the phone is connected to a specificcorporate network). If the confirmed location of the phone matches theregistered location, the emergency call is allowed to proceed.Otherwise, the emergency call should be “blocked” (i.e., disconnected).The use of registered locations ensures that any initiating device thatsuccessfully places an emergency call is known to be present at aspecific geographical location (i.e., the initiating device's registeredlocation) to which emergency services should be dispatched.

The use of registered locations can be especially limiting for mobiledevices (e.g., smartphones). By specifying a registered location fromwhich a mobile device can place VoIP emergency calls, a registeredlocation effectively forces the mobile device to function as a PSTNtelephone for the purposes of emergency calling.

An additional source of complication is the pending adoption oftext-based modes of communicating with emergency dispatchers (e.g.,“Text-to-911” functionality). As a practical matter, many VoIP callingprograms (e.g., Skype®) are capable of sending text messages. As in thecase of an emergency call, emergency services cannot be dispatched inresponse to a text message unless the geographical origin of that textmessage can be determined.

Accordingly, there is a need for a system and method to allow initiatingdevices to request emergency services from any location an emergencycall can be made or a text message requesting emergency services can besent.

BRIEF SUMMARY OF THE INVENTION

The present invention provides a way to place an emergency call from aninitiating device, such as a tablet computer, by routing the callthrough a proximate (i.e., nearby) proxy device, such as a smartphone.In an emergency, a user of an initiating device may attempt to place anemergency call (e.g., to 9-1-1) through the initiating device. Theinitiating device, however, may be unable to place the call because of alack of WiFi® or other network connectivity or the blocking ofVoIP-based or other network-based emergency calls under an informationtechnology (“IT”) or other policy. An IT policy may specify, forinstance, that a VoIP-based emergency call should be blocked when aninitiating device cannot be confirmed to be present at its registeredlocation. Upon the failure of an attempted VoIP-based emergency call,the initiating device emits a discovery signal to determine whether apaired proxy device is proximate. If the proxy device is proximate, theinitiating device directs the proxy device to initiate the emergencycall. If the proxy device successfully places an emergency call, theuser may speak with PSAP dispatcher through the proxy device.Alternatively, the initiating device may join the emergency call,allowing the user to speak with the PSAP dispatcher without switchingdevices.

In an embodiment, an initiating device detects a request for emergencyservices; determines that the device is away from a known location;confirms the proximity of a paired proxy device; and directs the proxydevice to send the request for emergency services.

In an embodiment, an initiating device may determine that it is awayfrom known location by: querying for location information from at leastone source; inferring the geographical location of the device from theresults of the query; and comparing the inferred location to the knownlocation.

In an embodiment, an initiating device may determine that it is awayfrom known registered location by determining that the device is unableto obtain location information from at least one source.

In an embodiment, an initiating device may confirm the proximity of apaired proxy device by: transmitting a discovery signal to the proxydevice; and receiving a reply signal from the proxy device.

In an embodiment, an initiating device may select an emergency number tocontact based on the location of the proxy device.

In an embodiment, the initiating device may join an emergency callinitiated by the proxy device.

In an embodiment, the known location may be a registered location forE911 calling.

In an embodiment, the request for emergency services may be a textmessage directed to an emergency number.

In an embodiment, an initiating device comprises a processor and amemory device. The memory device contains machine-readable instructionsthat control the initiating device to place an emergency call accordingto the foregoing process.

In an embodiment, a storage medium contains machine-readableinstructions that control an initiating device to place an emergencycall according to the foregoing process.

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used as an aid in determining the scope of the claimed subjectmatter. Other features and advantages will become apparent from thefollowing more detailed description, taken in conjunction with theaccompanying drawings, which illustrate, by way of example, theprinciples of the invention.

BRIEF DESCRIPTION OF DRAWINGS

The various present embodiments now will be discussed in detail with anemphasis on highlighting the advantageous features with reference to thedrawings of various embodiments. The illustrated embodiments areintended to illustrate, but not to limit the invention. These drawingsinclude the following figures, in which like numerals indicate likeparts:

FIG. 1A shows the relationship between an initiating device, a proxydevice, and a PSAP;

FIG. 1B is a schematic diagram showing components of an initiatingdevice and a proxy device;

FIG. 1C shows the relationship between an initiating device and sourcesof location information;

FIG. 2A is a flowchart depicting a process by which an initiating devicedirects a proxy device to place an emergency call;

FIG. 2B is a schematic diagram showing an inferred geographical locationthat is ambiguous with respect to a registered location; and

FIG. 2C is a schematic diagram showing an inferred geographical locationthat is not ambiguous with respect to a registered location.

DETAILED DESCRIPTION OF THE INVENTIONS

The following detailed description describes present embodiments withreference to the drawings. In the drawings, reference numbers labelelements of present embodiments. These reference numbers are reproducedbelow in connection with the discussion of the corresponding drawingfeatures.

As a preliminary note, any of the embodiments described with referenceto the figures may be implemented using software, firmware, hardware(e.g., fixed logic circuitry), or a combination of theseimplementations. The terms “logic,” “module,” “component,” “system” and“functionality,” as used herein, generally represent software, firmware,hardware, or a combination of these elements. For instance, in the caseof a software implementation, the terms “logic,” “module,” “component,”“system,” and “functionality” represent program code/instructions thatperforms specified tasks when executed on a processing device or devices(e.g., CPU, CPUs or processor(s)). The program code can be stored atlocations in one or more computer readable memory devices such as randomaccess memory, disc drives or their equivalents.

More generally, the illustrated separation of logic, modules,components, systems, and functionality into distinct units may reflectan actual physical grouping and allocation of software, firmware, and/orhardware, or can correspond to a conceptual allocation of differenttasks performed by a single software program, firmware program, and/orhardware unit. The illustrated logic, modules, components, systems, andfunctionality may be located at a single site (e.g., as implemented by asingle processing device), or may be distributed over a plurality oflocations and interconnected by a network.

The term “machine-readable media” and the like refers to any kind ofnon-transitory medium for retaining information in any form, includingvarious kinds of storage devices (magnetic, optical, static, etc.).Machine-readable media also encompasses transitory forms forrepresenting information, including various hardwired and/or wirelesslinks for transmitting the information from one point to another.

The embodiments disclosed herein, may be implemented as a computerprocess (method), a computing system, or as an article of manufacture,such as a computer program product or non-transitory computer-readablemedia. The computer program product may be computer storage media,readable by a computer device, and encoding a computer program ofinstructions for executing a computer process. The computer programproduct may also be a propagated signal on a carrier wave, readable by acomputing system, and encoding a computer program of instructions forexecuting a computer process.

The systems and processes described below are applicable and useful inthe upcoming cloud computing environment. Cloud computing pertains tocomputing capability that provides an abstraction between the computingresource and its underlying technical architecture (e.g., servers,storage, networks), enabling convenient, on-demand network access to ashared pool of configurable computing resources that can be rapidlyprovisioned and released with minimal management effort or serviceprovider interaction. The term “cloud” is intended to refer to theInternet and cloud computing allows shared resources, for example,software and information, to be available, on-demand, like a publicutility.

Typical cloud computing providers deliver common business applicationsonline, which are accessed from another web service or software like aweb browser, while the software and data are stored remotely on servers.The cloud computing architecture uses a layered approach for providingapplication services. The lowest layer is an application layer that isexecuted on client computers. In this example, the application allows aclient to access cloud storage. Above the application layer is a cloudplatform and cloud infrastructure, including a “server” layer thatincludes hardware and computer software designed for cloud-specificservices.

Referring to FIG. 1A, an embodiment of the invention may be part of aninitiating device 101. The initiating devices 101 can include, withoutlimitation, tablet computers, personal computers, laptop computers(e.g., a Microsoft Surface® product) or the like. More generally, aninitiating device 101 may be any device capable of placing VoIP callsthrough an Internet connection. By way of illustration but notlimitation, the initiating device 101 may be a desktop computer,smartphone, or smart watch running or accessing a VoIP calling program(e.g., Skype for Business™ software) or an analog telephone with anattached VoIP adapter. The initiating device 101 need not have“built-in” or “preconfigured” VoIP functionality. A laptop computer mayrequire a user to separately download and install a VoIP calling programbefore VoIP calls can be placed. Once the appropriate VoIP callingprogram is installed, however, the laptop computer becomes an initiatingdevice. The initiating device 101 is not precluded from havingadditional forms of network connectivity that allow for phone calls. Byway of illustration but not limitation, the initiating device 101 may bea smartphone running as a default cellular-network phone app in additionto a VoIP-calling app.

An initiating device 101 is associated (“paired”) with a proxy device102. A person skilled in the art will recognize that device-pairingfunctionality may be provided by an underlying technological standard(e.g., Wi-Fi Direct® or Bluetooth®). In a typical usage scenario, aproxy device 102 may be a smartphone. More generally, the proxy device102 may be any device capable of placing emergency calls through theE911 system. By way of illustration but not limitation, proxy device 102may be cellular-enabled and therefore capable of placing emergency callsthrough a cellular network (e.g., a 3G or 4G network), such as a tabletcomputer or smart watch with built-in support for cellular networks. Theproxy device 102 may be capable of sending a text message (e.g., viaShort Message Service) directed to an emergency number. The proxy device102, however, need not have “built-in” or “preconfigured” connectivityto a cellular network. By way of illustration but not limitation, theproxy device 102 may be a laptop computer equipped with a mobilebroadband adapter.

The initiating device 101 and the proxy device 102 are associated (orpaired) with one another, such that the devices 101, 102 are connectedin manner that allows either device to readily confirm the identity ofthe other device. Association 103 of the devices 101, 102 may beprovided by the device-pairing functionality of Wi-Fi Direct®technology. By way of illustration but not limitation, device-pairingmay be achieved using Wi-Fi Protected Access 2—Pre-Shared Key(conventionally called “WPA2-PSK” or “WPA2 Personal”) technology. Moregenerally, association 103 may be provided by any technology thatsupports device pairing (e.g., Bluetooth® or near-field communication.The association 103 between the devices 101, 102 may also be provided bya custom pairing technology. A custom pairing technology may bedesirable where either the initiating device 101 or the proxy device 102(or both devices 101, 102) does not support a standardized method ofpairing. Such may be the case, for instance, if proxy device 102 is afeature phone with no built-in support for Wi-Fi Direct®, Bluetooth, ornear-field communication. A custom pairing technology may require one orboth of the initiating device 101 and the proxy device 102 to haveadditional attached hardware (e.g., a dongle). The proxy device 102 iscapable of establishing a connection 104 to a PSAP 110.

In practice, the initiating device 101 may connect, through theInternet, to a VoIP server 104 operated by the provider of a VoIPcalling service (e.g., Skype®). The VoIP server 104 may optionally becapable of accessing a set of registered location records 105. The VoIPserver 104 may be connected to a PSTN gateway, which is in turnconnected to the PSTN, through which the PSAP 110 can be reached. Aperson skilled in the art will recognize that the VoIP server 104 andthe registered location records 105 may be implemented on a cloudcomputing platform.

Referring to FIG. 1B, the initiating device 101 includes a memory device101 a. The memory device 101 a may be any form of non-volatile storage.By way of illustration but not limitation, the memory device 101 a maybe a flash memory (e.g., in a smartphone or tablet computer), a magnetichard drive (e.g., in a laptop or desktop computer), or the like. Thememory device 101 a need not be an integral or “built-in” component ofthe initiating device 101. By way of illustration but not limitation,the memory device 101 a may be a removable memory card (e.g., a SecureDigital memory card), a USB flash drive, or a removable hard drive. Thememory device 101 a contains machine-readable instructions, which directthe processor 101 b to carry out the steps needed to cause an attemptedemergency call to be routed from the initiating device 101 to the proxydevice 102 (steps 210-240). The memory device 101 a may additionallycontain machine-readable instructions constituting a locationinformation service 101 c.

The initiating device 101 has a processor 101 b. The processor 101 b iscoupled to the memory device 101 a, such that the processor 101 b canaccess and execute machine-readable instructions stored on the memorydevice 101 a. The processor 101 b may be designed for use in a varietyof devices including, but not limited to, a smartphone or tabletcomputer (e.g., a Qualcomm® or ARM® processor) or for use in a laptop ordesktop computer (e.g., an Intel® or AMD® processor).

Referring to FIG. 1C, the initiating device 101 may communicate with avariety of sources of location information. As shown in FIG. 1C, theinitiating device may obtain location information from a cell tower(i.e., through cell-tower triangulation), a GPS satellite, or from a setof geolocation records (i.e., by associating an IP address with anestimated geographical location). A person skilled in the art willrecognize that the specific combination of sources reachable by theinitiating device 101 at any particular time may vary. If an initiatingdevice 101 is located in a basement, for instance, the initiating device101 will typically lack the ability to communicate with any cell toweror any GPS satellite. In practice, an initiating device 101 may obtainlocation information from multiple sources of the same type. Cell-towertriangulation, for example, requires the initiating device 101 tocommunicate with at least two cell towers. In addition to GPSsatellites, an initiating device 101 may also obtain information fromthe GLONASS satellite system (i.e., the Russian equivalent of GPS). Aninitiating device 101 may obtain location information from more than oneset of geolocation records.

Referring to FIG. 2A, the process for initiating an emergency call froman initiating device 101 begins when the initiating device 101 receivesa request to place an emergency call through VoIP (step 210). Therequest in step 210 may occur when a user of the initiating device 101dials an emergency number (e.g., “911”) or otherwise directs theinitiating device 101 to initiate an emergency call (e.g., by tapping an“Emergency Call” button on a user interface). Alternatively, step 210may by triggered by an automated system. By way of illustration but notlimitation, a “smart watch” could trigger step 210 upon the activationof an emergency-calling feature. The initiating device 101 then attemptsto place an emergency call through VoIP (step 220). If the VoIPemergency call is connected (outcome 220 a), then the user of theinitiating device 101 is connected to a PSAP, and the process ends.

The attempted VoIP emergency call in step 220, however, may beunsuccessful. The call may fail because of a lack of VoIP connectivity.Such may be the case, for instance, if initiating device 101 cannotreceive a Wi-Fi® or cellular signal of sufficient strength.Alternatively, the initiating device 101 may lack the authorization tocommunicate over any networks that are reachable. The initiating device101, for instance, may lack the credentials to access a secured Wi-Fi®network. Alternatively, the initiating device 101 may be prevented by adata cap from transmitting VoIP data over a cellular network.

The attempt in step 220 may also fail if VoIP emergency calling isdisabled for administrative reasons. An information technology (“IT”)policy, for instance, may specify that VoIP emergency calling isdisabled (“blocked”) when the initiating device 101 is cannot beconfirmed to be present at a registered location. Such blocking isuseful in preventing the initiating device 101 from causing emergencyservices to be dispatched on the basis of inaccurate information. Inpractice, the blocking of emergency calls from initiating devices may berequired by law or regulation. The attempt of step 220 may optionallyinclude the querying of a location information service (step 221) todetermine whether the initiating device 101 is present at a registeredlocation.

A registered location may be a street address (e.g., a residence) orother defined geographical area (e.g., a corporate campus). Theinitiating device 101 may determine whether it is present within aregistered location by inferring its current geographic location andcomparing the inferred location with the registered location. Theinferred location may be determined using location data obtained by theinitiating device 101. By way of illustration but not limitation, theinferred location may be coordinates from the Global Positioning System(“GPS”), Internet Protocol (“IP”) geolocation information, positionaldata from cell-tower triangulation, or a combination thereof. Theinferred location need not correspond exactly to the precise geographiclocation of the initiating device 101 to enable a determination ofwhether the initiating device 101 is present within a registeredlocation. For example, the registered location of the initiating device101 may be the headquarters of Microsoft (i.e., One Microsoft Way,Redmond, Wash. 98052). If the initiating device 101 is located at theMicrosoft Technology Center in New York City (i.e., 11 Times Square, NewYork, N.Y. 10036), IP geolocation information may indicate “New YorkCity” (without a street address) as the inferred location of theinitiating device 101. The fact that IP geolocation information wouldnot pinpoint the whereabouts of the initiating device 101 by streetaddress does not prevent the initiating device 101 from concluding thatit is outside its registered location. The fact that the inferredlocation is “New York City” is sufficient for the initiating device 101to conclude that it is outside its registered location.

FIGS. 2B and 2C illustrate the distinction between an ambiguous inferredlocation and a non-ambiguous inferred location. In both FIG. 2B and FIG.2C, an initiating device 101 has a registered location at One MicrosoftWay, Redmond, Wash. 89052. In FIG. 2B, the inferred location of theinitiating device 101 is Redmond, Wash. Such may be the case if the userof the initiating device 101 is somewhere within the city limits ofRedmond, Wash., and the initiating device 101 obtains the inferredlocation on the basis of IP geolocation information. Because theinferred location in FIG. 2B encompasses the registered location (i.e.,One Microsoft Way) as well as geographical locations outside theregistered location (i.e., elsewhere in Redmond, Wash.), the inferredlocation does not contain enough information to make a determination ofwhether the initiating device 101 is present at, or absent from, theregistered location. In FIG. 2C, by contrast, the inferred location isNew York, N.Y. Because geographical region encompassed by the inferredlocation is also the registered location, the initiating device canconclude that it is outside the registered location.

A person skilled in the art will recognize that some usage cases mayrequire the geographical location of the initiating device 101 to beknown with greater detail. In the foregoing example, the initiatingdevice 101 may instead be located in downtown Redmond, Wash., which isoutside the device's registered location. IP geolocation may indicate“Redmond, Wash.” as the current location of the initiating device 101.In that case, the IP geolocation information is insufficient todetermine whether the initiating device 101 is indeed within itsregistered location. Since the reported location of “Redmond, Wash.” maycorrespond to the registered location (i.e., One Microsoft Way) or someother location (e.g., downtown Redmond), there is no basis forconcluding whether the initiating device 101 is in a registeredlocation. In this case, additional information, such as GPS coordinates,may be needed to reach the correct determination. A person skilled inthe art will recognize that the various methods of determining thelocation of the initiating device 101 may be combined to reach anaccurate determination of whether the initiating device 101 is outsideits registered location.

In some cases, the initiating device 101 may be unable to determine itscurrent geographical location with sufficient accuracy to determinewhether the device is within a registered location. Such may be the caseif the initiating device 101 completely lacks connectivity to sources oflocation information. If the initiating device 101 is located in abasement, for instance, it may simultaneously lack Wi-Fi® connectivity,cellular connectivity, and visibility of GPS satellites. Alternatively,the initiating device 101 may find itself in circumstances where theonly available location information (e.g., IP geolocation information)is ambiguous. A person skilled in the art will recognize that when theinitiating device 101 cannot reach a determination as to whether it ispresent within a registered location, it is prudent to deem the deviceto be outside the registered location.

In practice, the initiating device 101 may obtain information concerningits own geographical location from a location information service. Alocation information service may be an application programming interface(“API”) that provides a uniform set of software commands for retrievinglocation information from disparate sources and for determining whetherthe initiating device 101 is away from a registered location. A locationinformation service may prioritize sources of location information. Byway of illustration but not limitation, a location information servicemay first attempt to determine the geographical location of theinitiating device 101 by retrieving GPS coordinates. If GPS coordinatescannot be obtained (e.g., because of a lack of visible GPS satellites),the location information service may then attempt to obtain IPgeolocation information. A location information service may combinelocation information from multiple sources, so as to determine thegeographical location of the initiating device 101 with greater accuracythan would be feasible with only information from any single source.Such an approach is particularly useful where high-accuracy sources oflocation information (e.g., GPS) are unavailable.

Following the failure of the attempted VoIP emergency call (outcome 220b), the initiating device 101 may ascertain the proximity of a proxydevice 102 (step 230). To determine whether the proxy device 102 isproximate to itself, the initiating device 101 transmits a wirelessdiscovery signal. The discovery signal may contain informationspecifically identifying the proxy device 102 as the desired respondent,or it may non-specifically request a response from any proxy device thatreceives the signal. If the proxy device 102 is within range of thediscovery signal, the proxy device 102 transmits a wireless replysignal. The wireless reply signal contains information confirming thatthe proxy device 102 is paired with the initiating device 101. Theinitiating device 101 may estimate the physical distance between itselfand the proxy device 102 by measuring the strength of the reply signal.Since the reply signal weakens with increasing distance between the twodevices, the initiating device 101 may define a minimum signal strength(“threshold strength”) as an indicator of proximity. If the strength ofthe reply signal is above the threshold strength, the proxy device 102is considered to be proximate to the initiating device 101; otherwise,the proxy device 102 is not proximate. The proxy device 102 may, forinstance, transmit the discovery signal at a power of 1.0 milliwatt(mW). A person skilled in the art will recognize that the signalstrengths may conventionally be expressed in decibel-milliwatts (dBm).Where decibel-milliwatts are used, a signal strength of 1 mW equates to0 dBm. Signal strengths greater than 1 mW will equate to positive dBmvalues, and signal strengths weaker than 1 mW will equate to negativedBm values. A person skilled in the art will recognize that it may beadvisable for the initiating device 101 to require the reply signal fromthe proxy device 102 to equal or exceed a threshold strength.

A person skilled in the art will recognize that the strength of thereply signal may be affected by environmental factors, such as thepresence of physical obstacles (e.g., walls or ceilings) between theinitiating device 101 and the proxy device 102. Therefore, the samestrength of reply signal, when received by the initiating device 101,may not always correspond to the same physical distance between theinitiating device 101 and the proxy device 102.

A person skilled in the art will recognize that the initiating device101 may confirm the proximity of the proxy device 102 by decoding atleast one specific network packet from the proxy device 102. By way ofillustration but not limitation, the decoded network packet mayconstitute a Transmission Control Protocol message, such as an a SYN-ACKmessage from the proxy device 102. A person skilled in the art willrecognize that the ability to decode at least one network packet fromthe proxy device 102 generally suffices to confirm the proximity of theproxy device 102, without any additional need to determine the strengthof the reply signal in milliwatts or decibel-milliwatts. This approachis advantageous because the wireless technology by which the devices101, 102 communicate may vary in maximum range. Bluetooth®, forinstance, has a maximum range of 10 meters while near-fieldcommunication has a maximum range of 20 centimeters.

The proxy device 102 may periodically transmit a reply signal regardlessof whether the initiating device 101 has transmitted a discovery signal.The periodical transmission of a reply signal allows the initiatingdevice 101 to monitor the proximity of the proxy device 102 on anongoing basis, thereby obviating the need to determine such proximitywhen a user of the initiating device 101 attempts to contact anemergency number. By way of illustration but not limitation, the proxydevice 102 may transmit a reply signal once every second.

The Bluetooth® low energy version of the Bluetooth® standard isparticularly suited for proximity detection. Because Bluetooth® lowenergy significantly reduces battery consumption while maintaining thesame wireless range as older versions of Bluetooth® technology, itallows the devices 101, 102 to engage in proximity detection withoutexcessively draining the battery of either device. Bluetooth® lowenergy, in addition, is expected to be available in more than 90% ofBluetooth®-enabled devices (e.g., tablet computers and smartphones) andto therefore enjoy near-ubiquitous support among mobile devices.

Wi-Fi Direct®, however, has some technological advantages overBluetooth® low energy, such as greater range support formore-sophisticated security measures. Where Wi-Fi Direct® providesproximity detection, the proxy device 102 may be configured to have thestatus of a Group Owner (“GO”) in accordance with WiFi® technologicalstandards. GO status allows the proxy device 102 to act as an accesspoint and to broadcast a Service Set Identifier (“SSID”) (i.e., awireless network name) and to make itself easily identifiable by theinitiating device 101. A person skilled in the art will recognize that aWiFi® access point periodically broadcasts “beacon frame” signals, whichidentify the existence and capabilities of that access point to allother Wi-Fi® devices within its range. A beacon frame includes aso-called “information element,” which can include information such asthe SSID associated with the access point. Where the proxy device 102acts as a Wi-Fi® access point, the proxy device 102 may additionally beconfigured to indicate in the information elements of its beacon framesthat it is available to contact emergency numbers. A person skilled inthe art will recognize that in addition to beacon frames, a Wi-Fi®access point is capable of broadcasting other types of “frame” signals,including “action frame” signals. An action frame may direct a receivingdevice to take a particular action. Thus, when the initiating device 101receives a request to contact an emergency number and is unable toconfirm that it is present in a registered location, the initiatingdevice 101 can transmit an action frame to the proxy device 102, whichdirects the proxy device 102 to contact the emergency number. Thesefeatures may make Wi-Fi Direct® preferable to Bluetooth® low energy inspecific usage scenarios.

If the proxy device 102 is not proximate to the initiating device 101(outcome 230 a), then the process ends with no emergency call placed.The initiating device 101 may alert the user, via an error message, thatno emergency call can be placed.

If the proxy device 102 is proximate to the initiating device 101(outcome 203 b), then the initiating device 101 directs proxy device 202to initiate an emergency call (step 240). The initiating device 101 maywirelessly transmit the emergency number to be dialed (e.g., “911”) tothe proxy device 102. The initiating device 101 may automatically selectan emergency number to be dialed by the proxy device 102 on the basis ofthe inferred location of the proxy device 101. In the European Union,for instance, the emergency number is 112 instead of 911. If anemergency arises when the initiating device 101 is being used in theEuropean Union, a United States-based user may not be aware that 112, isthe appropriate emergency number and may dial 911 instead. In this case,the initiating device 101 may automatically replace 911 with 112 whendirecting the proxy device 102 to initiate an emergency call.Alternatively, the initiating device 101 may show a message on a userinterface directing the user to dial an appropriate emergency numberusing the proxy device 102 (e.g., “Dial 911 on your mobile phone.”).

The proxy device 102 may not be able to place the emergency call(outcome 240 a). This may be the case if the proxy device 102 is unableto connect to any cell tower. In that event, the process ends and noemergency call is placed. The proxy device 102 may transmit a signal tothe initiating device 101 indicating this fact, and the initiatingdevice 101 may in turn alert the user, via an error message, that noemergency call can be placed.

If the proxy device 102 successfully places the emergency call (outcome240 b), then the user may speak to the PSAP dispatcher using proxydevice 102. Alternatively, the initiating device 101 may connect to theemergency call (e.g., through Wi-Fi Direct®), allowing the user to takepart in the emergency all without switching devices. If the initiatingdevice 101 joins the emergency call, the initiating device 101 maycapture audio and transmit that audio to the proxy device 102 (e.g.,through Bluetooth®, Wi-Fi Direct®, or near-field communication). Theproxy device 102 then transmits the audio through the PSTN to the PSAP110. Audio from the PSAP 110 is transmitted, in the reverse direction,through the proxy device 102 to the initiating device 101.

A person skilled in the art will recognize that the steps for placing anemergency call in FIG. 2 can be applied to text-message requests foremergency service. Where a user of the initiating device 101 requestsemergency services through a text message, the text message may beconsidered equivalent to an emergency call.

In some cases, the initiating device 101 and proxy device 102 mayconstitute a single physical device (“combined device”). Such may be thecase if, for instance, for a smartphone running both a PSTN calling app(e.g., the default “phone” app) and a VoIP calling app (e.g., Skype forBusiness™). In the case of a combined device, searching for a proximatedevice (step 230) may consist of verifying that a PSTN calling app isavailable on the device.

In some cases, the proxy device 102 may also constitute an initiatingdevice. Such may be the case, for instance, if the proxy device 102 is asmartphone running a VoIP calling app (e.g., Skype for Business™). Inthis case, the proxy device 102 may initiate a call using its own VoIPcalling app.

While the initiating device 101 is paired with a single proxy device 102in a typical usage scenario, the initiating device 101 may be associatedwith multiple proxy devices. Such may be the case, for instance, if auser carries separate mobile phones for personal and business use. Theinitiating device 101 may be configured to prioritize multiple proxydevices 102. The initiating device 101, for instance, may firstdetermine whether a business mobile phone is proximate. If the businessmobile phone is not proximate, the initiating device 101 may thendetermine whether a personal mobile phone is proximate. The initiatingdevice 101 may be configured to place an emergency call through thehighest-priority proxy device 102 that is proximate.

Throughout this specification the word “comprise”, or variations such as“comprises” or “comprising”, will be understood to imply the inclusionof a stated element, integer or step, or group of elements, integers orsteps, but not the exclusion of any other element, integer or step, orgroup of elements, integers or steps.

The use of the expression “at least” or “at least one” suggests the useof one or more elements or ingredients or quantities, as the use may bein the embodiment of the disclosure to achieve one or more of thedesired objects or results.

The numerical values mentioned for the various physical parameters,dimensions or quantities are only approximations and it is envisagedthat the values higher/lower than the numerical values assigned to theparameters, dimensions or quantities fall within the scope of thedisclosure, unless there is a statement in the specification specific tothe contrary.

The terminology used herein is for the purpose of describing particularexample embodiments only and is not intended to be limiting. As usedherein, the singular forms “a”, “an” and “the” may be intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. The terms “comprises,” “comprising,” “including,” and“having,” are inclusive and therefore specify the presence of statedfeatures, integers, steps, operations, elements, and/or components, butdo not preclude the presence or addition of one or more other features,integers, steps, operations, elements, components, and/or groupsthereof. The method steps, processes, and operations described hereinare not to be construed as necessarily requiring their performance inthe particular order discussed or illustrated, unless specificallyidentified as an order of performance. It is also to be understood thatadditional or alternative steps may be employed.

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the claims that follow is notnecessarily limited to the specific features or acts described above.Rather, the specific features and acts described above are disclosed asexample forms of implementing the claims.

1. An initiating device capable of placing VoIP calls comprising: a processor; a memory device containing machine-readable instructions that control the device to: detect a request for emergency services; determine whether the initiating device is or is not confirmably present at a registered location; upon determining the initiating device is not confirmably present at the registered location, confirm a proximity within a range of a proxy device to the initiating device; and upon confirming the proximity within a range of the proxy device, route the request for emergency services through the proxy device.
 2. The initiating device of claim 1, wherein the proxy device is capable of connecting to a cellular network.
 3. The initiating device of claim 1, wherein routing the request for emergency services comprises directing the proxy device to send the request to initiate an emergency call.
 4. The initiating device of claim 1, wherein routing the request for emergency services comprises blocking the request if the proximity of a proxy device cannot be confirmed.
 5. The initiating device of claim 1, wherein determining whether the initiating device is or is not confirmably present at a registered location comprises: querying for location information from at least one source; inferring the geographical location of the device from the results of the query; and comparing the inferred location to the registered location.
 6. The initiating device of claim 1, wherein confirming the proximity within a range of the proxy device comprises: transmitting a discovery signal to the proxy device; and receiving a reply signal from the proxy device.
 7. The initiating device of claim 1, wherein routing the request for emergency services comprises selecting an emergency number based on the location of the proxy device.
 8. A storage device containing instructions that direct an initiating device capable of placing VoIP calls to: detect a request for emergency services; determine whether the initiating device is or is not confirmably present at a registered location; upon determining the initiating device is not confirmably present at the registered location, confirming a proximity within a range of a proxy device to the initiating device; and upon confirming the proximity within a range of the proxy device, route the request for emergency services through the proxy device.
 9. The storage device of claim 8, wherein routing the request for emergency services comprises directing the proxy device to send the request to initiate an emergency call.
 10. The storage device of claim 8, wherein routing the request for emergency services comprises blocking the request if the proximity within a range of a proxy device cannot be confirmed.
 11. The storage device of claim 8, wherein determining whether the initiating device is or is not confirmably present at a registered location comprises: querying for location information from at least one source; inferring the geographical location of the initiating device from the results of the query; and comparing the inferred location to the registered location.
 12. The storage device of claim 8, wherein confirming the proximity within a range of the proxy device comprises: transmitting a discovery signal to the proxy device; and receiving a reply signal from the proxy device.
 13. The storage device of claim 8, wherein routing the request for emergency services comprises selecting an emergency number based on the location of the proxy device.
 14. A method of placing an emergency call from an initiating device capable of placing VoIP calls, the method comprising: detecting, by the initiating device, a request for emergency services; determining, by the initiating device, whether the initiating device is or is not confirmably present at a registered location; upon determining the initiating device is not confirmably present at the registered location, confirming, by the initiating device, a proximity within a range of a proxy device to the initiating device; and upon confirming the proximity within a range of the proxy device, routing, by the initiating device, the request for emergency services through the proxy device.
 15. The method of claim 14, wherein routing the request for emergency services comprises directing, by the initiating device, the proxy device to send the request to initiate an emergency call.
 16. The method of claim 14, wherein routing the request for emergency services comprises blocking, by the initiating device, the request if the proximity within a range of a proxy device cannot be confirmed.
 17. The method of claim 14, wherein determining whether the initiating device is or is not confirmably present at a registered location comprises: querying for location information from at least one source; inferring the geographical location of the initiating device from the results of the query; and comparing the inferred location to the registered location.
 18. The method of claim 14, wherein confirming the proximity within a range of the proxy device capability comprises: transmitting, by the initiating device, a discovery signal to the proxy device; and receiving, by the initiating device, a reply signal from the proxy device.
 19. The method of claim 14, wherein routing the request for emergency services comprises selecting, by the initiating device, an emergency number based on the location of the proxy device.
 20. The method of claim 14, wherein the proxy device is capable of connecting to a cellular network. 